Skip to content

Conversation

@CarlyAThomas
Copy link
Contributor

  • Change develop server port from 3000 to 3001
  • Change mock-fcc-data port from 3001 to 3002

Checklist:

Reason
This allows classroom to run alongside freeCodeCamp's main platform for integration testing. fCC Proper uses ports 3000 (backend) and 8000 (frontend), which conflicts with classroom's default port 3000.

Testing
✅ Verified npm run develop starts on port 3001
✅ Verified npm run mock-fcc-data starts on port 3002
✅ Confirmed no port conflicts when running both services simultaneously

- Change develop server port from 3000 to 3001
- Change mock-fcc-data port from 3001 to 3002
- This allows classroom to run alongside fCC Proper (ports 3000/8000)
@NewtonLC NewtonLC self-requested a review December 6, 2025 02:27
Copy link
Contributor

@NewtonLC NewtonLC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For these port changes to be accepted, they should also be reflected in documentation and environment files, such as .env.sample, .codespace-instructions.sh, and .gitpod.yml.

@CarlyAThomas CarlyAThomas requested a review from a team as a code owner December 6, 2025 02:39
- Update README.md with port information in setup steps
- Update .env.sample with new NEXTAUTH_URL and mock data URL
- Update codespace-instructions.sh with new port URLs
- Update .devcontainer/devcontainer.json forwardPorts array

These changes ensure documentation reflects the new port
configuration that avoids conflicts with freeCodeCamp's main
platform (ports 3000/8000).
@CarlyAThomas CarlyAThomas force-pushed the chore/update-dev-ports branch from d68ca85 to 6595fc0 Compare January 9, 2026 03:31
@CarlyAThomas
Copy link
Contributor Author

I have added instructions for Auth0 in the readme with the corrected ports as well as updates for the environment files .env.sample and .codespace-instructions.sh.

Per request, gitpod instructions and notation is being removed in another PR and thus .gitpod.yml has not been modified here see PR #573.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants